Purpose

Adds a Java port of the Work Item Filtering split activities scenario sample (samples/scenarios/WorkItemFilteringSplitActivitiesJava), using the standalone Durable Task SDK (not Durable Functions). This demonstrates the new useWorkItemFilters() API from durabletask-java v1.9.0 to route orchestration and activity work items to dedicated workers.

Note: Work item filtering for Java is currently supported only in the standalone Durable Task SDK (durabletask-client / durabletask-azuremanaged). It is not yet available in the Durable Functions Java extension.

What's included

• 4 standalone Java services (Gradle multi-project build):
  • Orchestrator Worker — registers only OrderProcessingOrchestration
  • Validator Worker — registers only ValidateOrder activity
  • Shipper Worker — registers only ShipOrder activity
  • Client — schedules orchestration batches in a loop and prints results
• Shared ConnectionHelper — builds DTS connection strings from environment variables (emulator, Managed Identity, DefaultAzure)
• Dockerfiles for each service (Eclipse Temurin 21)
• Bicep infrastructure and azure.yaml for one-command azd up deployment to Azure Container Apps with KEDA scaling
• README with architecture diagram, step-by-step local run instructions, expected output, and Azure deployment guide

How it works

Each worker calls .useWorkItemFilters() on the DurableTaskGrpcWorkerBuilder to auto-generate filters from registered tasks. DTS routes work items only to workers with matching filters — no cross-processing occurs.

Tested locally

Verified end-to-end against the DTS emulator (mcr.microsoft.com/dts/dts-emulator:latest):

• All 3 orchestrations per batch complete successfully
• Orchestrator Worker handles only orchestration replays
• Validator Worker handles only ValidateOrder activities
• Shipper Worker handles only ShipOrder activities

Related

• Java SDK PR: Adding work item filters support microsoft/durabletask-java#275
• .NET equivalent (also standalone SDK, not Durable Functions): samples/scenarios/WorkItemFilteringSplitActivities
• Quickstart doc: https://learn.microsoft.com/azure/durable-task/scheduler/quickstart-work-item-filtering-durable-task

Does this introduce a breaking change?

• Yes
• No

Pull Request Type

What kind of change does this Pull Request introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Documentation content changes
• Other... Please describe:

How to Test

• Get the code

git clone https://github.com/Azure-Samples/Durable-Task-Scheduler.git
cd Durable-Task-Scheduler
git checkout vabachu/work-item-filters-java

• Start the DTS emulator

docker pull mcr.microsoft.com/dts/dts-emulator:latest
docker run -d --name dts-emulator -p 8080:8080 -p 8082:8082 mcr.microsoft.com/dts/dts-emulator:latest

• Build the sample

cd samples/scenarios/WorkItemFilteringSplitActivitiesJava
./gradlew build

• Start the three workers (each in a separate terminal)

./gradlew :orchestrator-worker:run
./gradlew :validator-worker:run
./gradlew :shipper-worker:run

• Run the client (in a fourth terminal)

./gradlew :client:run

What to Check

Verify that the following are valid:

• Client schedules 3 orchestrations per batch and all complete successfully
• Orchestrator Worker logs only orchestration processing (no activity execution)
• Validator Worker logs only ValidateOrder activity work items
• Shipper Worker logs only ShipOrder activity work items
• Stopping Shipper Worker causes ShipOrder work items to remain pending (not routed to other workers)
• Restarting Shipper Worker causes pending ShipOrder work items to complete immediately

Other Information

• Requires Java 21+ and Docker
• Uses durabletask-client:1.9.0 and durabletask-azuremanaged:1.9.0 from Maven local (not yet published to Maven Central)
• This is a standalone Durable Task SDK sample — work item filtering is not yet available in the Durable Functions Java extension